Problem Note 65243: Records might be written to the System Exception folder or placed in a SavedE state during the batch import process
 |  |  |  |
In SAS® Merchandise Allocation, records might be written to the System Exception folder or placed in a SavedE state during the batch import process. This issue is likely to occur during the save process to the MAXDATA.ALLOC_DEF table when some columns are not populated. The issue occurs when the interface server thread count for concurrent processing (batchimport.concurrent.request.count) is set to a value greater than 1.
The following exceptions are generated in the catalina.out log:
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (MAXDATA.PK_ACTIVE_TEMPLATE_CACHE) violated ORA-00001: unique constraint (MAXDATA.PK_ACTIVE_TEMPLATE_CACHE) violated Exception in insert:
[ERROR] [batchImport] handler.MMAXImportManager - Alloc Version not found for commonMerchLevel=16 : commonMerchID=-1. Writing to System Exception Folder.
java.sql.SQLSyntaxErrorException: ORA-00904: "LV8CMAST_IDLV8CTREE_ID": invalid identifier
java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
There is no workaround for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Merchandise Allocation | 64-bit Enabled AIX | 4.2 | 4.3 | 9.4 TS1M5 | 9.4 TS1M5 |
| Linux for x64 | 4.2 | 4.3 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2012 R2 Std | 4.2 | 4.3 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2020-01-06 11:35:27 |
| Date Created: | 2019-12-11 12:49:35 |